Website management is the process of configuring and maintaining the appearance, navigation structure, and content authoring environment for Content Management (WCM) websites. Website management comprises the following activities:
■ Defining the appearance and navigation structure of websites.
■ Defining the infrastructure for the web content authoring environment.
■ Performing website maintenance.
Putting it all together
Website management comprises three general workflows:
■ The process of defining the appearance and navigation structure of your CM websites entails the following actions, which should generally be performed in the order shown:
□ Defining website look and feel, by choosing a specific mix of available master pages and themes.
□ Defining sitemaps (navigation items) to build the navigation structure of your website.
□ (optional) Defining shortcut URLs to enable the use of short, "reader-friendly" links to important pages of your website.
■ The process of creating the infrastructure to support the people who perform web content authoring entails the following actions, which should generally performed in the order shown:
□ Defining content authority groups (CAGs) to grant various content authoring permissions to the people who will perform web content authoring in your organization.
□ Defining content folders to organize the creation of content records.
□ (optional) Enabling workflow for content authoring for specific content folders to enable better coordination of web content authoring efforts among the people responsible for developing and maintaining the content records in those folders.
□ (optional) Defining content layouts to extend the basic set of content layouts provided with CM, thereby enabling new arrangements of the iParts in a content record.
□ Defining tags and defining tagged list formats (see Defining tagged list formats) for use in content record properties and certain types of iParts to enable tag-filtered searches and the creation of dynamic content that changes automatically based on the tags assigned to content records in the system.
□ (optional) Defining CM user-defined fields (UDFs) to enable capturing additional properties of the content in content records, which can enable CM website visitors to perform more powerful website searches, and can provide additional filtering and sorting of the output of ContentTaggedList iParts.
□ (optional) Importing content from a staging server if you choose to develop and test new content and navigation outside of your production environment.
■ The process of website maintenance entails the following actions, performed as needed:
□ Managing the priority of pending publication requests to speed up a publishing request that is behind many others in the publishing queue.
□ Viewing CM reports to gain information about your websites and web content authoring efforts.